Configure SBC Communication Mode

You can determine the method that is used by User Management Pack 365 to communicate with SBC devices including Autodiscovery, Websocket, direct connection or by using a custom address. Following the wyUpdate upgrade, the SBC communication path is automatically set to Direct connection (Fqdn).

Do the following:
1. In the Known SBCs page, select an SBC device, and then from the Actions drop-down, select Edit.

2. From the SBC Communication path drop-down, choose the relevant value according to the table below.

Parameter

Description

Direct connection (FQDN)

Connect to Live Platform server directly by configuring the FQDN Public IP address of the SBC device.

After wyUpdate upgrade, the SBC communication path is automatically set to Direct connection (FQDN), which is received from Live Platform.

Direct connection (IP)

Connect to OVOC server directly by configuring the Private IP address of the SBC device.

Use Autodiscover

Automatically determines the best communication path in the following priority:

WebSocket
IP Address
FQDN
Custom IP address

Use Websocket

Connect to the SBC through Websocket tunnel, routed via OVOC. This option allows User Management Pack 365 SP Edition to communicate with SBC devices that are located behind a NAT or firewall when their HTTP/HTTPS ports are open. This option requires the following configuration:

Ensure the SBC device is connected to OVOC via Websocket
Add the following new rows in ‘ApplicationSettings’ table in the UMP SQL database (the values depend on the method your UMP-365 is connected to OVOC). See Networking:
Ovoc.WsProxy.DiscoveryPort
8061 if UMP-365 is connected to OVOC via Websocket
80 if UMP-365 is connected to OVOC with HTTP
443 if UMP-365 is connected to OVOC with HTTPS
Ovoc.WsProxy.EndpointPort
8060 if UMP is connected to OVOC via Websocket
80 if UMP is connected to OVOC with HTTP
443 if UMP is connected to OVOC with HTTPS

Custom address

Connect to OVOC using a Custom IP address.

Not in Use

-

Not Manually Set

-